[Bot] NPM Packages Release UE5.7#811
Open
github-actions[bot] wants to merge 1 commit intoUE5.7from
Open
Conversation
185aeea to
73fb08f
Compare
73fb08f to
9605309
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to UE5.7, this PR will be updated.
Releases
@epicgames-ps/lib-pixelstreamingfrontend-ue5.7@0.3.0
Minor Changes
Patch Changes
npm run lintwill now run linting over all packages.npm run lintwork regardless of the directory it's invoked from. Each workspace'seslint.config.mjsnow pinsparserOptions.tsconfigRootDirtoimport.meta.dirname, soparserOptions.projectresolves relative to the config file's own directory rather than whichever CWDtypescript-eslinthappens to pick by default. Previously the six workspace configs prefixedprojectwith the workspace directory (e.g.'Common/tsconfig.cjs.json'), which only worked under one specifictypescript-eslintversion's resolution behavior and broke CI when run from within the workspace.@epicgames-ps/lib-pixelstreamingfrontend-ui-ue5.7@0.2.0
Minor Changes
Patch Changes
npm run lintwill now run linting over all packages.npm run lintwork regardless of the directory it's invoked from. Each workspace'seslint.config.mjsnow pinsparserOptions.tsconfigRootDirtoimport.meta.dirname, soparserOptions.projectresolves relative to the config file's own directory rather than whichever CWDtypescript-eslinthappens to pick by default. Previously the six workspace configs prefixedprojectwith the workspace directory (e.g.'Common/tsconfig.cjs.json'), which only worked under one specifictypescript-eslintversion's resolution behavior and broke CI when run from within the workspace.@epicgames-ps/lib-pixelstreamingsignalling-ue5.7@0.3.0
Minor Changes
--rest_apibut without--serve. Previously the Express app that hosts the/api/*routes was only bound to an HTTP listener inside theservebranch, so with--serve=false --rest_api=truethe listener never started and requests were answered by the WebSocket upgrade handler on the player port (426 Upgrade Required). The HTTP listener now starts wheneverrest_apiorserveis set. Static file serving and the homepage route are gated by a newIWebServerConfig.serveStaticflag (the port listener runs independently of static serving), and the rate limiter is registered before any route handlers so the homepage and any downstream-registered routes are all rate-limited. Wilbur logs at startup which mode it is running in.Patch Changes
npm run lintwill now run linting over all packages.npm run lintwork regardless of the directory it's invoked from. Each workspace'seslint.config.mjsnow pinsparserOptions.tsconfigRootDirtoimport.meta.dirname, soparserOptions.projectresolves relative to the config file's own directory rather than whichever CWDtypescript-eslinthappens to pick by default. Previously the six workspace configs prefixedprojectwith the workspace directory (e.g.'Common/tsconfig.cjs.json'), which only worked under one specifictypescript-eslintversion's resolution behavior and broke CI when run from within the workspace.@epicgames-ps/lib-pixelstreamingcommon-ue5.7@0.1.5
Patch Changes
npm run lintwill now run linting over all packages.npm run lintwork regardless of the directory it's invoked from. Each workspace'seslint.config.mjsnow pinsparserOptions.tsconfigRootDirtoimport.meta.dirname, soparserOptions.projectresolves relative to the config file's own directory rather than whichever CWDtypescript-eslinthappens to pick by default. Previously the six workspace configs prefixedprojectwith the workspace directory (e.g.'Common/tsconfig.cjs.json'), which only worked under one specifictypescript-eslintversion's resolution behavior and broke CI when run from within the workspace.@epicgames-ps/wilbur@3.0.2
Patch Changes
npm run lintwork regardless of the directory it's invoked from. Each workspace'seslint.config.mjsnow pinsparserOptions.tsconfigRootDirtoimport.meta.dirname, soparserOptions.projectresolves relative to the config file's own directory rather than whichever CWDtypescript-eslinthappens to pick by default. Previously the six workspace configs prefixedprojectwith the workspace directory (e.g.'Common/tsconfig.cjs.json'), which only worked under one specifictypescript-eslintversion's resolution behavior and broke CI when run from within the workspace.--rest_apibut without--serve. Previously the Express app that hosts the/api/*routes was only bound to an HTTP listener inside theservebranch, so with--serve=false --rest_api=truethe listener never started and requests were answered by the WebSocket upgrade handler on the player port (426 Upgrade Required). The HTTP listener now starts wheneverrest_apiorserveis set. Static file serving and the homepage route are gated by a newIWebServerConfig.serveStaticflag (the port listener runs independently of static serving), and the rate limiter is registered before any route handlers so the homepage and any downstream-registered routes are all rate-limited. Wilbur logs at startup which mode it is running in.